How To - Configuring Aztec Promotions & Discounts


Promotions

Any rewards intended for Loyalty need to be first configured within Aztec as a promotion or discount, and all promotions intended for use within Loyalty should have a trigger button created in order for the promotion to fire.

For example, a Loyalty Reward could be one free beer each month, and a corresponding Aztec Promo named 'BOGOF'. First, create a trigger button in Product Modelling called something appropriate (such as loyalty free beer).



Make a note of the entity code as this will be required when setting up the reward within the loyalty platform


Create your promotion as normal using BOGOF, with two groups defined as below



Then price as below:



The trigger button now needs to be added to the theme; this button should not be made visible on the till itself but should be hidden on a specific local panel as below:



Discounts

In this example, we have set up a Loyalty Reward of '20% off all food for loyalty card holders', with the corresponding Aztec discount of 20%.

To achieve this, create the discount as normal within Theme Modelling, followed by Estate Settingsand finally Discounts.




Be sure to make a note of the discount ID, in this case "9", as this will be required when creating the corresponding reward within the Loyalty platform


Unlike promotional triggers, loyalty discounts should not be mapped anywhere onto the theme including a hidden panel, but instead should be added into base data as follows:

  • Navigate to Base Data, followed by Estate Structureand Site, and lastly the CLM Tab.



Once Edit Discounts has been selected you will be able to choose the relevant loyalty discounts for this site.



For a site to be able to use any loyalty rewards set up, the following buttons will need to be added to their tills:


Allows a loyalty card to be assigned to an account

Checks the points/cash balance of a particular card

Allows applicable prizes/rewards to be redeemed against the account

Cancels any prizes/rewards added in error